-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[buildkite] Fix "Codegen" test in buildkite pipeline #4312
base: master
Are you sure you want to change the base?
Conversation
…ainer created by proto-gen.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to figure out a way to get a consistent protoc compiler version here; otherwise we're likely to run into trouble.
$UID_FLAGS $PROTOC_IMAGE_VERSION \ | ||
--gogofaster_out=${resolve_protos},plugins=grpc:/src \ | ||
-I/src -I/src/github.com/m3db/m3/vendor ${proto_files} | ||
protoc --gogofaster_out=${resolve_protos},plugins=grpc:${GOPATH}/src \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should try to stick with the containerized protobuf here ideally--we want to use a consistent protobuf version, rather than whatever the developer has "lying around".
RUN apt-get update && apt-get install -y lsof netcat-openbsd docker.io jq | ||
RUN apt-get update && apt-get install -y lsof netcat-openbsd docker.io jq protobuf-compiler thrift-compiler | ||
|
||
RUN go install github.com/gogo/protobuf/protoc-gen-gogofaster@latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment--we want a consistent set of versions for this.
What this PR does / why we need it:
This PR fixes "Codegen" test in buildkite pipeline.
Fixes #4274
Special notes for your reviewer:
Does this PR introduce a user-facing and/or backwards incompatible change?:
No
Does this PR require updating code package or user-facing documentation?:
No